No output #6
No output #6
Conversation
|
@aborruso Do we need the output files gitted? |
| @@ -4,6 +4,7 @@ set -x | |||
| set -e | |||
| set -u | |||
| set -o pipefail | |||
| alias mlr='mlr.linux.x86_64' | |||
There was a problem hiding this comment.
@NikosAlexandris my mlr executable is mlr not mlr.linux.x86_64. Using this line will I have problems?
There was a problem hiding this comment.
Oops! This is something local! I shouldn't have committed it.
yes, why not? Why you want backtick in |
Now it's |
Because the output will be generated when the user wants or when a page or the manual is rebuild. It's the end product of the script. Hmm, I am thinking that I should maybe work on a development branch, where I/we don't need to recommit the end-product with each and every single change of the script. And let it be as is for the main branch? But, ok. It was just an idea to avoid recommitting the end-product and just do it once and a while. |
No description provided.